Configuration

If you followed the directions for software setup and unzipped the kit files with C:\HTTPD as your server root, you can skip this step for now. The server and document roots are pre-configured as shipped to work "out of the box" from this root. Any changes you make to the configuration files increase your chances for failure.

I don't need to configure now!

These rules apply to all of httpd's configuration files.

Unix Path Syntax: Use "/" in all configuration pathnames
Case insensitive: These files are not case sensitive.
Comment lines begin with #: Lines which should be ignored begin with #, the hash sign. This must be the first character on the line. Comments must be on a line by themselves.
One directive per line : Each line in these files consists of:
directive data
directive is a keyword httpd recognizes, followed by one space. data is specific to the directive.
Extra whitespace is ignored: You can put extra spaces or tabs between directive and data. To embed a space in data without separating it from any subsequent arguments use a \ character before the space.

There are four configuration files:

The Server Configuration File
The Server Resource Map
The Global Access Configuration File
The MIME Types Configuration File (don't touch!)

We strongly recommend that you thoroughly familiarize yourself with the documentation regarding these files. In particular, do not modify the Types configuration file. Use the AddType directive instead. This server is very capable and flexible, and it is very easy to misconfigure if you aren't clear about what you are doing. You have been warned.

Back to Installation Overview

Back to Administration Overview

Robert B. Denny <rdenny@netcom.com>